Quick Start Guide

You will communicate with the chatbot via Telegram.

If you are not registered yet, download and install Telegram from the official website.

Once installed, open the Diologi chatbot: @diologi_IoT_bot

Tap the Menu button and select Start.

Create a New Project

A project usually represents one building.
It can include multiple field devices (controllers or supervisors) and can be shared with other Telegram users.

1. Open the Main Menu and Navigate to Settings → Projects

   

2. Tap New project and give it a short, meaningful name
   

   

Add a New Device

A device represents a physical on-site device that connects to the chatbot via MQTT.

note

If your device uses another protocol (e.g. BACnet, Modbus), an MQTT gateway must be used.
In this case, the gateway itself is treated as a device by the chatbot.

1. Go to Main Menu → Settings → Devices and select the project you just created

2. Tap New device and enter a short, meaningful device name

Connect Your Device

1. Open the Device list and choose your newly created device

   

2. Open Security and select Issue certificate

   
   
   tip

   Save the Device ID shown in the information message — you will need it later.

3. Select Certificate Type

   Choose one option depending on your device:

• Separate files - CA certificate, device certificate, and private key as separate files
  (common for most devices)

• Full chain - Single file containing CA certificate, device certificate, and private key
  (common for Niagara / Niagara-based supervisors)

  note

  Only one active certificate per device is allowed.
  If a certificate is lost, it must be revoked and reissued.

4. MQTT Connection Settings

   After downloading the certificates, upload them to your MQTT device and configure. For device-specific instructions, see the Connecting your device section or use the common settings below.

• MQTT host / Broker Endpoint:

    mqtt.diologi.com

• Port:

    8883

• MQTT Client ID: Your Device ID

• TLS: Enabled

• MQTT version: 5.0

  tip

  You can find the Device ID in Settings selecting your device from the list

5. Verify Connection

   Return to the Device list and open your device.
   If everything is configured correctly, the status will change to Connected.

Set Up MQTT Communication

Once the device is connected, upload the excel file with project settings and MQTT point list.

1. First, download the Excel file containing the existing project settings. Go to Settings → Projects → Project list, select your project, and tap Export to xlsx. You can use it as a template if you have just created the project.

2. Open the downloaded Excel file and fill in the required fields

point_id

• Leave empty on first import - it will be generated automatically
• If removed later, the point will be recreated and history will be lost
• If kept, the point will be updated and history preserved

menu_structure

Defines project hierarchy and navigation in the chatbot.

• Use / as separator
• Allowed characters: letters, digits, spaces, underscores
• Segment length: 3–30 characters

incoming_topic

MQTT subscription topic for messages coming into the chatbot.

• Must start with the Device ID
• Use / as separator
• Must not start or end with /
• Max length: 300 characters
• Allowed characters: letters, digits, underscores

outgoing_topic

MQTT publishing topic for messages sent from the chatbot. The same rules apply as for incoming_topic.

note

MQTT topics on your field device must exactly match the topics defined in the Excel file, including the device ID at the beginning.

point_mode

Defines how the chatbot interacts with the point

• Subscribe - the chatbot only subscribes to the point to read values from the device.
• Publish - the chatbot subscribes to the point and can also publish values back to the device. New values can be set via the Set value menu or using an AI command.

point_type

• Float - decimal numbers
• Boolean - TRUE / FALSE
• Integer - whole numbers

float_format

Defines the number of decimal places using the format .#, where # is the number of decimals.

For example, if the device sends 21.1234:

• 0 → displays 21 in the chatbot
• .1 → displays 21.1
• .2 → displays 21.12
• ...

float_publish_range

Limits writable float values.

Format: min, max

For example: 10.0, 75.5

selector_range

Maps numeric values to meaningful labels.

Examples:

• Boolean: true: 'Alarm', false: 'No alarm'
• Integer: 0: 'Off', 1: 'On', 2: 'Auto'

Limits:

• Description length: 1–30 characters
• Key value length: 1–6 digits

This is the minimum configuration required to get your project running. After completing the file, save and import it back via Project settings.

Additionally, you can configure notifications, history logging, and AI-based interaction to communicate with the bot using natural language.

Notifications

To enable notifications, fill in the notification_on column in the project settings Excel file.

Trigger on specific values

• For boolean points use TRUE or FALSE.
• For integers use a comma-separated list of values, e.g.: 0, 1, 2

Trigger when outside a range (for floats)

• To limit only one side of the range, use a single condition, e.g.: <=10.5
• To limit both sides, use two conditions separated by a comma: <=10.5, >75.2

You can pause notifications for a specific project and user via the Project settings menu.

To view active notifications, tap Active alerts in the main menu or simply ask the bot using a text message.

History

Enable history logging by filling the history column.

Supported formats:

##d - every ## days
##h - every ## hours
##m - every ## minutes
##s - every ## seconds
##ms - every ## milliseconds

AI interaction

When you communicate with the chatbot using natural language, the AI engine relies on the following fields:

• menu_structure
• selector_range
• meta_info

The more accurately and uniquely these fields describe each point, the better the AI can map user requests to the project structure and implement required functions.

meta_info Use this field for additional context. There is no need to duplicate information already present in other fields. Typical use cases include:

• Location
  (e.g. Room 301, Level 3, Block 2, Reception)
• Adding technical details
  (e.g. pressure switch is interlocked with primary ASHP pumps)
• Grouping systems by common function when it’s not obvious from menu_structure
  (e.g. HWS, ASHP secondary circuit)

Often, meta_info will contain the same information for multiple points, especially when used for location data. For example, temperature and humidity sensors in the same room, or multiple rooms served by the same AHU.

Maximum length: 500 characters

Auto status check

When sending a control command, you can ask the AI to verify whether the command was successful by defining a status feedback point. For example, check a fan DPS on the AHU start command.

To do this, add the following to the meta_info field of the control point:

StatusCheck: "point_name"

Rules:

• Status and control points must be in the same submenu
• Monitoring lasts 5 minutes after the command
• The result is determined based on point names and their selector_range, so make sure selector descriptions are clear and meaningful.

Start using the bot

Once the project settings file is filled in and successfully imported, you can start using the bot.

Use the menu to:

• Check system status and View live readings
• Change setpoints or switch equipment on/off
• Check actlive alerts

Ensure that values are updating correctly and that communication between the bot and field devices is stable.

You can test AI functionality by asking, for example:

• Show project info
• Show plant info (e.g. Show me AHU1 info)
• Show the list of pre-set notifications
• Show active alarms
• Show temperature readings for AHU1
• Change a setpoint or switch a plant on/off

note

Although the bot understands natural language, AI functionality is limited to supported intents. We continuously expand these capabilities and will notify you as new features become available.

Share the project

You can share a project with other telegram users registered in the chatbot.

Ask the user to send you their Telegram username, which can be found in Telegram → Settings → Username.

If no username is set, it must be created by tapping Edit profile (top right) and filling in the Username field.

Once you have the username, navigate to Project settings, select your project from the list and tap Share.

Enter the Telegram username and assign a role:

• ADMIN — full access, including project settings
• USER — full operational functionality, without access to project settings

Example: @diologiuser USER

When a project is shared, the user will receive a notification from the chatbot. You can revoke access at any time from the same project settings menu.

note

Each project must have at least one user with the ADMIN role.